Test/migration workflow #628
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses Android part of: synonymdev/bitkit-e2e-tests#83
Description
This PR schedules the E2E migration workflow (introduced in #598) to run nightly.
The workflow executes four migration scenarios:
Each scenario:
• Creates a wallet in the RN app (including transactions, tags, and a standard Lightning channel)
• Triggers the migration flow
• Verifies migration success by validating balances, transactions, and tags
The tests cover migrations from the last three Bitkit RN versions:
• v1.1.6
• v1.1.4
• v1.1.3
For migration setup, prebuilt Bitkit RN apps for regtest are used. These builds are published here:
https://github.com/synonymdev/bitkit-e2e-tests/releases/tag/migration-rn-regtest
I think that running this workflow nightly provides sufficient coverage.
Migration scenarios were implemented in:
synonymdev/bitkit-e2e-tests#95
Preview
Example run: https://github.com/synonymdev/bitkit-android/actions/runs/21136659237
QA Notes